Multilingual Entity Fields

DRUID simplifies the authoring process for NER management in multi-language bots. Multilingual entity fields and NER enable DRUID bots to align entity records (e.g., healthcare specialties, product names, city names, etc.) with the current chat user's language. These multilingual entity fields can be regarded as aliases for language-specific field clones.

Set multilingual entity fields

To designate an entity field as multilingual, simply enable the Holds multilanguage records option in the field configuration page.

Upon saving the entity field, DRUID automatically generates associated field clones to store language-specific values for all tenant bot languages. These clones follow a naming convention of <fieldname>_<LanguageCode> and are not visible in Entity Designer. DRUID utilizes these clone fields to match entity records aligned with the current chat user's language.

Multilingual entity fields and NER

In the context of multlingual bots, multilingual entity fields play a crucial role in NER. They facilitate the validation of user input against a list of predefined values specific to the current user's language ([[ChatUser]].Language). DRUID NLP seamlessly identifies multilingual entity fields, creating language-specific NER indexes and utilizing the corresponding language-specific clone fields.

Manage multilingual entity fields

Should you decide to revert an entity field from being multilingual, simply disable the Holds multilanguage records option. You have the choice to either automatically delete the auto-generated field clones or handle their deletion manually. Disabling this option may impact conversational flows, especially if clone fields are utilized in flow or integration tasks. For streamlined management, DRUID provides the flexibility to review conversational flows and manually remove field clones accordingly.

Choosing Handle Manually will make the auto-generated language specific field(s) visible in Entity Designer and you can review the conversational flows and remove the field clones afterwords.

To automatically delete the field clones, click Delete. All auto-generated language specific field(s) will be deleted on entity field save.

Language-specific field clones in bot language changes

When adding additional languages to a bot, DRUID automatically creates language-specific entity fields (field clones) for all existing multilingual entity fields. Similarly, when introducing a new bot language, DRUID generates entity fields for that language, including field clones for multilingual entity fields. Deleting a bot language unique to your tenant enables the removal of language-specific entity fields, allowing for a thorough review of conversational flows without impacting dialogs.

Using multilingual entity fields on flows and integrations

In flow settings and integration tasks, leverage multilingual entity fields to enhance functionality. The Flow Engine seamlessly integrates language-specific clone fields, utilizing them if populated. However, use language-specific clone fields in flows only when explicitly necessary. For NER in multilingual bots with expected language-specific values from external databases, ensure proper mapping of language-specific values to DRUID language-specific field clones in the database response.